Skip to content

feat(workflows): use-workflow_call-events#465

Merged
ReenigneArcher merged 1 commit intomasterfrom
feat/workflows/use-workflow_call-events
Jun 11, 2025
Merged

feat(workflows): use-workflow_call-events#465
ReenigneArcher merged 1 commit intomasterfrom
feat/workflows/use-workflow_call-events

Conversation

@ReenigneArcher
Copy link
Copy Markdown
Member

@ReenigneArcher ReenigneArcher commented Jun 10, 2025

Description

This PR does heavy refactoring of the workflows. The main change is that global workflows will now call another workflow. This will reduce the frequency of changes in individual repositories as we can just update the workflows in this repo and each repo will automatically point to the latest changes. There are also additional changes listed below.

  • Remove unused workflows/files:
    • .github/label-actions.yml
    • .github/workflows/issues.yml
    • .github/workflows/patch_missing_releases.yml
  • Minor changes:
    • workflows not meant to be replicated are prefixed with __
    • workflows that are replicated are prefixed with _ (indicating that this file should not be modified in the individual repositories)
    • add .venv to .flake8 config file
    • add targetUrl to semantic.yml config file

Unfortunately, this will require updating branch protection rules. This may be a good opportunity to migrate to the new rule sets.

TODO:

  • test
  • change uses target back to @master
  • use local __call workflow when running from this repo

Screenshot

Issues Fixed or Closed

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Dependency update (updates to dependencies)
  • Documentation update (changes to documentation)
  • Repository update (changes to repository files, e.g. .github/...)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

@ReenigneArcher ReenigneArcher force-pushed the feat/workflows/use-workflow_call-events branch 11 times, most recently from 210fa96 to 876dc5f Compare June 10, 2025 03:40
@ReenigneArcher ReenigneArcher marked this pull request as ready for review June 10, 2025 03:53
@ReenigneArcher ReenigneArcher force-pushed the feat/workflows/use-workflow_call-events branch from 876dc5f to aa46a2f Compare June 10, 2025 03:56
@ReenigneArcher ReenigneArcher marked this pull request as draft June 10, 2025 03:58
@ReenigneArcher ReenigneArcher force-pushed the feat/workflows/use-workflow_call-events branch from aa46a2f to 7f2eab7 Compare June 11, 2025 01:09
@ReenigneArcher ReenigneArcher force-pushed the feat/workflows/use-workflow_call-events branch from 7f2eab7 to e75d7cf Compare June 11, 2025 01:13
@sonarqubecloud
Copy link
Copy Markdown

@ReenigneArcher ReenigneArcher marked this pull request as ready for review June 11, 2025 01:17
@ReenigneArcher ReenigneArcher merged commit 85b2e6b into master Jun 11, 2025
13 checks passed
@ReenigneArcher ReenigneArcher deleted the feat/workflows/use-workflow_call-events branch June 11, 2025 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant